Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.claude/skills/ably-review/SKILL.md:
- Around line 102-106: Update the skill's flag-architecture check to not require
clientIdFlag for REST mutation commands: modify the instructions around the
grep/list of flag spreads (productApiFlags, clientIdFlag, durationFlag,
rewindFlag, timeRangeFlags, ControlBaseCommand.globalFlags) and the rule in step
3 so it only mandates clientIdFlag for commands that create a realtime
connection (e.g., publish, subscribe, presence enter/subscribe, spaces
enter/get/subscribe, locks acquire/get/subscribe, cursors set/get/subscribe,
locations set/get/subscribe, or call space.enter()), and explicitly exclude
REST-only mutations like update/delete/append from requiring clientIdFlag; keep
the LSP goToDefinition guidance for ambiguous imports to verify flags resolve to
src/flags.ts.

In `@README.md`:
- Around line 1395-1428: The fenced code blocks added for the CLI usage/examples
are missing language tags and trigger markdownlint warnings; update each
triple-backtick fence (the usage/help blocks such as the
"USAGE/ARGUMENTS/FLAGS/DESCRIPTION/EXAMPLES" blocks) to include a language tag
like text (e.g., ```text) so the generated help remains readable and the
markdownlint warnings are cleared.

In `@src/commands/channels/append.ts`:
- Around line 41-55: The flags object for this REST-only command incorrectly
includes clientIdFlag; remove clientIdFlag from the static override flags spread
so the class no longer exposes --client-id (leave productApiFlags intact), and
verify there are no references to clientIdFlag elsewhere in this file (e.g., in
run() which creates an Ably REST client) so compilation/type checks still pass.

In `@src/commands/channels/publish.ts`:
- Around line 271-282: The per-message success path in publish flow ignores
publishResult.serials for multi-message publishes: capture
publishResult?.serials[0] into serial (as you already do) but ensure this serial
is attached to the per-message result object and included in the emitted
messagePublished payload for count > 1; update the code around
publisher(message) / publishResult / result (and the emission of
messagePublished) to always include serial when defined (i.e., add serial to the
result and to the event payload rather than omitting it for multi-message
flows).

In `@src/utils/message.ts`:
- Around line 33-43: The parsing logic in the message builder drops or
misassigns an "extras" field when extracting name and data; update the flow
around the existing message/messageData/flags handling so that if
messageData.extras exists you move it into message.extras (and delete it from
messageData) before deciding on message.data, and when deciding message.data use
"data" in messageData first, otherwise if messageData has other keys (after
removing extras and name) assign that object to message.data, but do not treat a
sole extras object as data; ensure you delete moved keys from messageData to
avoid duplication.

In `@test/unit/commands/channels/append.test.ts`:
- Around line 10-25: Remove the top-level describe("channels:append command",
...) wrapper so the file's five required describe suites live at the top level;
keep the existing beforeEach(getMockAblyRest), retain
standardHelpTests("channels:append", import.meta.url),
standardArgValidationTests("channels:append", import.meta.url, { requiredArgs:
[...] }), standardFlagTests("channels:append", import.meta.url, [...]) and the
local describe blocks for "functionality" and "error handling" unchanged,
ensuring the final file contains exactly the five top-level describe blocks
named 'help', 'argument validation', 'functionality', 'flags', and 'error
handling'.

In `@test/unit/commands/channels/delete.test.ts`:
- Around line 10-22: Remove the extra outer describe("channels:delete command")
wrapper and replace it with exactly five top-level describe blocks named "help",
"argument validation", "functionality", "flags", and "error handling"; call
standardHelpTests("channels:delete", import.meta.url) inside the "help" block,
standardArgValidationTests("channels:delete", import.meta.url, { requiredArgs:
["test-channel"] }) inside the "argument validation" block, and
standardFlagTests("channels:delete", import.meta.url,
["--json","--description"]) inside the "flags" block, and move getMockAblyRest()
into a beforeEach that applies to the "functionality" and "error handling"
blocks (or a top-level beforeEach outside the describe blocks) so the mocks are
initialized for those suites; ensure the five describe block names match
exactly.

In `@test/unit/commands/channels/update.test.ts`:
- Around line 10-25: Remove the extra outer suite wrapper
describe("channels:update command") and its matching closing brace so the file
only contains the five required describe blocks provided by the helper calls;
keep the getMockAblyRest() invocation but move it into a top-level beforeEach
(or into the appropriate individual describe blocks) instead of inside the
removed wrapper — adjust the current beforeEach that calls getMockAblyRest()
accordingly and ensure the helper calls standardHelpTests,
standardArgValidationTests, and standardFlagTests remain unchanged.

---

Outside diff comments:
In @.claude/skills/ably-codebase-review/SKILL.md:
- Around line 120-126: Update the SKILL.md rule so the codebase-review skill
does not require clientIdFlag for all mutation commands; instead, limit
clientIdFlag enforcement to commands that create realtime connections as defined
by the coding guidelines (e.g., publish, subscribe, presence enter/subscribe,
spaces enter/get/subscribe, locks acquire/get/subscribe, cursors
set/get/subscribe, locations set/get/subscribe, and any command that calls
space.enter()); modify the cross-reference block (the paragraph that currently
says "Commands creating realtime connections or performing mutations (publish,
update, delete, append) must have clientIdFlag") to remove mutations and list
the exact allowed command types, keeping the identifier clientIdFlag and
ensuring ControlBaseCommand.globalFlags and other rules remain unchanged.